[Matching Brackets] draft approaches#3670
Conversation
|
Do you have any idea why |
No clue, really. Probably trying to be "helpful" by linting. A question for Erik, methinks. |
|
OK, thanks. I'll put something on the forum. |
|
Welcome back! I am, as usual, very happy with your changes. |
colinleach
left a comment
There was a problem hiding this comment.
I'm happy with these changes
Hopefully, the final edits. 😄
|
Tryin' to make my way back, slowly. 😅 . Just about done with this, and after one more once-over, will approve and merge! |
|
In your own time. Let me know if there's anything I can do to help. I'm also feeling my way back in. Today's submission (julia/two-bucket) was my first solution for >2 months. |
|
Alrighty. Let's hope that I didn't re-confuse left vs right. I think everything's all good...so pushing the big, green button! 🚀 |
|
WOOT! One down, 17 more to go....... |
|
Yeah, I don't think I'll PR any more just yet (for so many reasons) |
* [Matching Brackets] draft approaches * [Matching Brackets] Approaches Review & Edits * Additional grammar and spelling edits * Final Edits Hopefully, the final edits. 😄 * Un crossed left vs right --------- Co-authored-by: BethanyG <BethanyG@users.noreply.github.com>
This one ended up less short and boring than I expected, with benchmarking totally invalidating my predictions!
As an aside, this is the second approaches submission that needs to refer to Walrus operators - now occurring regularly in community solutions. Whatever the low current priority of the learning syllabus, it would make my life easier to have PR #3585 merged so that we can reference it.